Systems and methods for activating account card functions based on physical device interactions

ABSTRACT

Systems and methods are provided for activating a function of an account card based on physical devices interactions such as a motion pattern detected by the account card. In some embodiments, the account card may include one or more sensors and processing capabilities sufficient to store a motion pattern, detect a motion pattern representing movement of the account card, compare the detected motion pattern to the stored motion pattern, and activate one or more functions of the account card based on the comparison. In some embodiments, the one or more functions may relate to account information communication, such as writing a magnetic stripe, unblocking a magnetic stripe, activating a near field communication chip, displaying an account number, providing power to an antenna, or otherwise enabling communication of the account number based on the capabilities of the card.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is entitled to and claims the benefit of priority fromU.S. Provisional Application No. 62/203,042 filed Aug. 10, 2015, thecontents of which are expressly incorporated herein by reference.

BACKGROUND

Account cards are used in many aspects of daily life, including gainingaccess to secure locations, providing identifying information, andperforming monetary transactions. In some situations, mobile devicessuch as smartphones are replacing traditional cards, such as mobiledevices having apps for making payments at point-of-sale locations oraccessing a hotel room. But traditional cards still remain the mostcommonly-used mechanism for providing account information, thanks totheir small form factor, convenience, and the highly developedinfrastructure for receiving account information from cards such asmagnetic card readers.

Compared to mobile electronic devices, traditional cards have moreinherent security risks. While mobile electronic devices are usuallylocked with a passcode or PIN to prevent unauthorized usage, traditionalcards are inherently unlocked and can be used by anyone in possession ofthe card. Thus, when a card is lost or stolen, the finder or thief canuse the card at will, until an intervening event occurs, such as thecard issuer disabling the card, a diligent cashier refusing the cardupon checking the cardholder's identification, or destruction of thecard. Often times, card issuers and the true cardholders suffer theconsequences of fraudulent activities by the time the card number iscancelled or changed.

In view of the shortcomings of current systems and methods for providingaccount information, a robust, secure, and efficient mechanism forcontrolling activation of account card devices is desired.

SUMMARY

Disclosed embodiments provide systems and methods for activating accountcard functions based on physical gestures.

Consistent with a disclosed embodiment, an apparatus for providingaccount information is provided. The apparatus may comprise a housing, apower source, at least one sensor, a data transmitter, a memory storinginstructions and account information, and a processor. The processor maybe configured to execute the stored instructions to detect, using the atleast one sensor, a motion pattern corresponding to a physical gestureperformed using the apparatus, and activate, based on the detectedmotion pattern, the data transmitter to provide the stored accountinformation.

Consistent with another disclosed embodiment, a method for providingaccount information is provided. The method may comprise detecting, by adevice including at least one processor in communication with at leastone sensor, a motion pattern corresponding to a physical gestureperformed using the device, and activating, based on the detected motionpattern, the data transmitter to provide account information stored in amemory in the device.

Consistent with other disclosed embodiments, non-transitorycomputer-readable storage media may store program instructions, whichare executed by at least one processor device and perform any of themethods described herein.

The foregoing general description and the following detailed descriptionare exemplary and explanatory only and are not restrictive of theclaims.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate several embodiments and, togetherwith the description, serve to explain the disclosed principles. In thedrawings:

FIG. 1 is a diagram of an exemplary system that may be used to activateaccount card functions using physical gestures, consistent withdisclosed embodiments.

FIG. 2 is a diagram of an exemplary mobile device, consistent withdisclosed embodiments.

FIG. 3 is a diagram of an exemplary account card, consistent withdisclosed embodiments.

FIG. 4 is a flowchart of an exemplary account card setup process,consistent with disclosed embodiments.

FIG. 5 is a flowchart of another exemplary account card setup process,consistent with disclosed embodiments.

FIG. 6 is a flowchart of an exemplary account information transmissionprocess, consistent with disclosed embodiments.

DESCRIPTION OF THE EMBODIMENTS

The disclosed embodiments are directed to systems and methods foractivating account card devices using physical device interactions suchas gestures. In particular, systems and methods allow users to activateone or more functions of an account card using physical gestures, suchas a pattern of motion. Some of the disclosed embodiments provide newaccount card hardware having specialized components for activating theaccount card. Some of the embodiments provide specialized methods andprocesses for programming and using the account card.

In some embodiments, physical gestures may include one or more movementsperformed in a sequence that results in a motion pattern. Movements mayinclude, for example, vertical shaking, horizontal shaking, randomshaking, twisting, twirling, drawing a picture or character(s) in air,tapping, flipping, positioning in a certain orientation, sliding, andany other type of physical movement capable of detection using one ormore known sensors.

In some embodiments, an account card of an approximate size and shape ofa traditional card may have embedded electronics capable of detecting amotion pattern corresponding to a physical gesture that a user performswhile holding the account card. One or more processors in the accountcard may detect the motion pattern, and compare the motion pattern to apreviously-recorded motion pattern, to verify a matching pattern. If themotion pattern matches, then the processor may activate one or morefunctions of the account card, enabling the account card to transmitaccount information. For example, the processor may write accountinformation to a magnetic stripe of the account card, allowing themagnetic stripe to provide the account information when the account cardis read in a standard card reader. As another example, the processor mayactivate a near field communication (NFC) chip to allow transmission ofaccount data, whereas prior to detecting the motion pattern, the NFCchip would not activate. Therefore, the account card may only becomeuseful for providing account information once a verified motion patternis detected, and users may benefit from the added levels of security ina card form-factor.

Reference will now be made in detail to exemplary embodiments, examplesof which are illustrated in the accompanying drawings and disclosedherein. Wherever convenient, the same reference numbers will be usedthroughout the drawings to refer to the same or like parts.

FIG. 1 shows a diagram of an exemplary system 100 that may be configuredto perform one or more processes for enabling transmission of accountinformation based on detection of a motion pattern. The components andarrangements shown in FIG. 1 are not intended to limit the disclosedembodiments, as the components used to implement the disclosed processesand features may vary.

In accordance with disclosed embodiments, system 100 may include accountcard 110, mobile device 115, card information receiver 120, cardinformation recipient server 125, card issuer server 130, database 135,network 140, and local network 145. Other components known to one ofordinary skill in the art may be included in system 100 to gather,process, transmit, receive, and provide information used in conjunctionwith the disclosed embodiments.

Account card 110 and/or mobile device 115 may be associated with a user105. In some embodiments, user 105 is an individual associated with oneor more accounts. In some embodiments, account card 110 may comprise anID card, a membership card, a credit card, a debit card, an ATM card, agift card, or any other type of card associated with at least oneaccount. Those of ordinary skill in the art will appreciate that thepresent embodiments may be used to enable transmission of any type ofdata stored on account card 110, and the present embodiments are notlimited to account information such as account numbers.

Mobile device 115 may be a personal computing device such as, forexample, a mobile device with computing ability, a tablet, smartphone,wearable device such as Google Glass™ or smart watches, a generalpurpose or notebook computer, or any combination of these computersand/or affiliated components. In one embodiment, mobile device 115 maybe a computer system or mobile computer device that is operated by user105 who is associated with an account for which account card 110 isissued.

Card information receiver 120 may comprise one or more computerizeddevices configured to receive account information. In some embodiments,card information receiver 120 may include a magnetic stripe reader, anear field communication (NFC) transceiver, an RFID reader, a wirelessantenna, a barcode scanner, or any other type of device capable ofreceiving account information.

Card information recipient server 125 may be operated by one or moreentities that wish to receive account information. Such entities (notshown in figures) may include, for example, a government agency, astore, a bank, an ATM, a library, a hotel, a membership facility such asa fitness center, a restaurant, and any other type of individual ororganization that requests and receives information from individuals.Card information recipient server 125 may be a computer-based systemincluding computer system components, desktop computers, workstations,tablets, hand held computing devices, memory devices, and/or internalnetwork(s) connecting the components. In some embodiments, cardinformation receiver 120 and card information recipient server 125 maybe located region 101, and geographically separated from card issuerserver 130 and/or database 135. In some embodiments, user 105 may visitregion 101 and provide account information to card information recipientserver 125 via account card 110 and card information receiver 120.

Card issuer server 130 may include one or more computer-based systemsincluding computer system components, desktop computers, workstations,tablets, hand held computing devices, memory devices, and/or internalnetwork(s) connecting the components. Card issuer server 130 may beowned and/or operated by an entity responsible for issuing (e.g.,creating or authorizing the creation of) account card 110 andmaintaining one or more accounts associated with account card 110. Insome embodiments, card issuer server 130 is associated with one or moreof a membership facility such as a fitness center, a governmentorganization such as a state government or department of motor vehicles,a bank, a credit card company, a hotel, or any other entity that mayissue cards such as account card 110, and maintain one or more accounts.

Database 135 may include one or more memory devices that store data andinstructions used to perform one or more features of the disclosedembodiments. Database 135 may also include any combination of one ormore databases controlled by memory controller devices (e.g., server(s),etc.) or software, such as document management systems, Microsoft SQLdatabases, Share Point databases, Oracle™ databases, Sybase™ databases,or other relational databases. In some embodiments, database 135 maycomprise an associative array architecture, such as a key-value storage,for storing and rapidly retrieving large amounts of information about anindividual. In some embodiments, database 135 may store informationassociated with one or more accounts, such as an account associated withaccount card 110 and user 105.

Network 140 may comprise any type of computer networking arrangementused to exchange data. For example, network 140 may be the Internet, aprivate data network, virtual private network using a public network,and/or other suitable connection(s) that enables system 100 to send andreceive information between the components of system 100. Network 140may also include a public switched telephone network (“PSTN”) and/or awireless network such as a cellular network, WiFi network, or otherknown wireless network capable of bidirectional data transmission.

Local network 145 may comprise any type of computer networkingarrangement used to exchange data in a localized area, such as WiFi,Bluetooth™′ Ethernet, and other suitable network connections that enablecomponents of system 100 to interact with one another and to connect tonetwork 140 for interacting with components in system environment 200.In some embodiments, local network 145 comprises a portion of network140. In other embodiments, components of system 100 may communicate vianetwork 140, without a separate local network 145.

FIG. 2 shows a diagram of an exemplary mobile device 115, consistentwith disclosed embodiments. As shown, mobile device 115 may include adisplay 210, input/output (“I/O”) devices 220, one or more processors230, memory 240 having stored thereon one or more programs 250, such asaccount app 252, and also storing data 260, and may further include anantenna 270 and one or more sensors 280. One or more of display 210, I/Odevices 220, processor(s) 230, memory 240, antenna 270, or sensor(s) 280may be connected to one or more of the other devices depicted in FIG. 2.Such a connection may be accomplished using a bus or otherinterconnecting device.

I/O devices 220 may include one or more devices that customer device 110to receive input from user 105 and provide feedback to user 105. I/Odevices 220 may include, for example, one or more buttons, switches,speakers, microphones, or touchscreen panels. In some embodiments, I/Odevices 220 may be manipulated by user 105 to input information intomobile device 115.

Processor 230 may be one or more known processing devices, such as amicroprocessor from the Pentium™ or Atom™ families manufactured byIntel™, the Turion™ family manufactured by AMD™, the Exynos™ familymanufactured by Samsung™, or the Snapdragon™ family manufactured byQualcomm™. Processor 230 may constitute a single core or multiple coreprocessors that executes parallel processes simultaneously. For example,processor 230 may be a single core processor configured with virtualprocessing technologies. In certain embodiments, processor 230 may uselogical processors to simultaneously execute and control multipleprocesses. Processor 230 may implement virtual machine technologies, orother known technologies to provide the ability to execute, control,run, manipulate, store, etc. multiple software processes, applications,programs, etc. In another embodiment, processor 230 may include amultiple-core processor arrangement (e.g., dual, quad core, etc.)configured to provide parallel processing functionalities to allowmobile device 115 to execute multiple processes simultaneously. One ofordinary skill in the art would understand that other types of processorarrangements could be implemented that provide for the capabilitiesdisclosed herein.

Memory 240 may be a volatile or non-volatile, magnetic, semiconductor,tape, optical, removable, non-removable, or other type of storage deviceor tangible (i.e., non-transitory) computer-readable medium that storesone or more program(s) 250 such as account app 252, and data 260. Data260 may include, for example, user 105's personal information, accountinformation, and display settings and preferences. In some embodiments,account information may include items such as, for example, analphanumeric account number, account label, account balance, accountissuance date, account expiration date, account issuer identification, agovernment ID number, a room number, a room passcode, and any othernecessary information associated with user 105 and/or an accountassociated with user 105, depending on the needs of user 105, entitiesassociated with card information recipient server 125, and/or entitiesassociated with card issuer server 130.

Program(s) 250 may include operating systems (not shown) that performknown operating system functions when executed by one or moreprocessors. By way of example, the operating systems may includeMicrosoft Windows™, Unix™, Linux™′ Apple™, or Android™ operatingsystems, Personal Digital Assistant (PDA) type operating systems, suchas Microsoft CE™, or other types of operating systems. Accordingly,disclosed embodiments may operate and function with computer systemsrunning any type of operating system. Mobile device 115 may also includecommunication software that, when executed by a processor, providescommunications with network 140, such as Web browser software, tablet,or smart hand held device networking software, etc. Mobile device 115may be a device that executes mobile applications for performingoperations consistent with disclosed embodiments, such as a tablet ormobile device.

Program(s) 250 may include account app(s) 252, such as an account foractivating, setting up, and configuring account card 110. In someembodiments, account app 252 may include instructions which causeprocessor 230 to connect to account card 110 and/or card issuer server130 via a direct wireless connection, via network 140, or via localnetwork 145. In some embodiments, account app 252 may configure accountcard 110 by detecting a motion pattern, verifying the detected motionpattern, and transmitting the motion pattern to account card 110 forstorage and later comparison. In some embodiments, account app 252 mayallow user 105 to configure settings for one or more motion patternsassociated with account card 110.

Sensors 280 may include one or more devices capable of sensing theenvironment around mobile device 115 and/or movement of mobile device115. In some embodiments, sensors 280 may include, for example, anaccelerometer, a shock sensor, a gyroscope, a position sensor, amicrophone, an ambient light sensor, a temperature sensor, and/or aconductivity sensor.

FIG. 3 shows a diagram of an exemplary account card 110, consistent withdisclosed embodiments. As shown, account card 110 may include processor310, display 320, memory 330, power source 340, one or more sensors 350,input devices 360, antenna 370, and magnetic stripe 380. In someembodiments, account card 110 may include more or fewer components thanshown in FIG. 3. As depicted in FIG. 3, one or more of processor 310,display 320, memory 330, power source 340, one or more sensors 350,input devices 360, antenna 370, and magnetic stripe 380 may be connectedto one or more of the other devices depicted in FIG. 3. Such aconnection may be accomplished using a bus or other interconnectingdevice.

In some embodiments, account card 110 may comprise an ID card, amembership card, a credit card, a debit card, an ATM card, a gift card,or any other type of card associated with at least one account. In someembodiments, account card 110 may comprise a device worn and/or carriedby user 105 such as, for example, a fob, a key fob, a wristband, anecklace, or any other portable electronic device. In some embodiments,account card 110 may include at least one data transmitter for providingaccount information, such as magnetic stripe 380, or antenna 370, suchas a near field communication chip or a short range wirelesstransceiver.

Processor 310 may comprise one or more known or specialized processingdevices, of sufficient size and form factor to fit within a card such asaccount card 110. In some embodiments, processor 310 may constitute asingle or multiple core processor capable of performing functionsrelated to the disclosed methods such as, for example, controlling powersource 340, sending and receiving data, reading and writing memory 330,receiving and analyzing data from sensors 350, generating informationfor presentation on display 320, receiving and processing input from I/Odevices 360, and any other functions consistent with the disclosedembodiments.

Display 320 may comprise a screen, indicator light, or other appropriatedevice for displaying a status or message to user 105. In someembodiments, display 320 may include a small LCD screen, e-ink screen,or OLED display. In other embodiments, display 320 may include one ormore Light Emitting Diodes (LEDs). In some embodiments, display 320 mayprovide notifications, prompts, and/or messages to user 105, such asstatus messages indicating whether account card 110 is powered on,whether account card 110 is ready to detect a motion pattern, whether adetected motion pattern is verified or requires verification, whetheraccount information is transmitting or successfully transmitted, and anyother notifications and messages consistent with disclosed embodiments.

Memory 330 may include a volatile or non-volatile, magnetic,semiconductor, or other type of storage device or tangible (i.e.,non-transitory) computer-readable medium that stores one or more motionpatterns, account information, computer-executable instructions, and insome embodiments, one or more settings associated with one or morestored motion patterns.

Power source 340 may include a power storage device such as a battery orcapacity, a power receiver such as an inductive power coil or a wirelesspower receiver, a power generator such as a solar or kinetic powergenerator, or any combination thereof. In some embodiments, power source340 may include one or more other known devices capable of generating,receiving, and/or storing electricity. In some embodiments, power source340 may be combined or integrated with sensor 350, such as apiezoelectric sensor configured to detect motion and to generateelectricity from the detected motion.

In some embodiments, account card 110 may receive power from an externalsource, such as wireless power or inductive power. In such embodiments,power source 340 may automatically activate in response to a sufficientlevel of ambient power, and power source 340 may provide power toprocessor 310 to activate account card 110. In some embodiments, accountcard 110 may include a generator which produces energy in response tomovement, sunlight, and any other known power generation means capableof fitting within account card 110. In such embodiments, power source340 may continue generating power and storing generated power in abattery or capacitor of power source 340, for later use. In someembodiments, power source 340 may comprise a battery or capacitor sealedwithin account card 110, either having an external charging port or nocharging port, requiring replacement of account card 110 upon depletionof power source 340. In other embodiments, power source 340 may comprisea removable and/or replaceable battery or capacitor.

Sensors 350 may include one or more devices capable of sensing theenvironment around account card 110 and/or movement of account card 110.In some embodiments, sensors 350 may include, for example, anaccelerometer, a shock sensor, a gyroscope, a position sensor, amicrophone, an ambient light sensor, a temperature sensor, and/or aconductivity sensor.

In some embodiments, processor 310 may detect motion patterns associatedwith multiple sensors, such as a sequence of taps on a first side ofaccount card 110, followed by a sequence of taps on a second side ofaccount card 110. In some embodiments, account card 110 may detect suchmotion patterns using a single sensor 350, such as a multi-axisaccelerometer. In some embodiments, account card 110 may includemultiple sensors 350 located on different sides, edges, or faces ofaccount card 110 to detect complex motion patterns.

Input devices 360 may include one or more buttons, switches, or otherforms of input mechanisms for receiving an indication or instructionfrom user 105. In some embodiments, input devices 360 may receive asequence or series of inputs, to cause processor 310 to perform variousfunctions associated with the disclosed embodiments.

In some embodiments, account card 110 may include antenna 370, fortransmitting and/or receiving data from one or more external locations.Antenna 370 may comprise a short-range wireless antenna, a near-fieldcommunication chip, or other device.

In some embodiments, account card 110 may include magnetic stripe 380,which may be controlled by processor 310. For example, processor 310 maywrite, clear, and rewrite magnetic stripe 380, to provide particularaccount information once account card 110 is activated and has detecteda verified motion pattern.

FIG. 4 is a flowchart of an exemplary account card setup process 400,consistent with disclosed embodiments. In the example shown in FIG. 4,process 400 is performed by processor 310 of account card 110. In someembodiments, however, some or all steps of process 400 may be performedby a processor other than processor 310. Those of ordinary skill mayalso understand that process 400 may include more or fewer steps, andsome steps may be performed in a different order than illustrated inFIG. 4.

In step 402, processor 310 may activate account card 110. In someembodiments, processor 310 may detect an initial power-up, such asactivation of power source 340, or an input received via input devices360. In some embodiments, account card 110 may activate in response todata detected from one or more sensors 350, such as an ambient lightsensor. For example, user 105 may remove account card 110 from a wallet,and account card 110 may activate when the ambient light sensor becomesexposed to light. In other embodiments, account card 110 may activate inresponse to movement that causes power source 340 to generate sufficientelectricity to power processor 310, such as a kinetic energy generator.

In step 404, processor 310 may determine whether a motion pattern ispreprogrammed in memory 330. In some embodiments, card issuer server 130may preprogram a motion pattern into account card 110 memory 330, sothat user 105 need not perform process 400, but instead may begin usingaccount card 110 immediately. For example, a hotel or fitness center maywish to use a single motion pattern for all guests and members, toprevent non-guests and non-members from using the cards. In suchembodiments, card issuer server 130 may generate and store a motionpattern in memory 330, which all guests and members may use to activatetheir account cards. If processor 310 determines that a motion patternis preprogrammed (“yes” in step 404), then process 400 may end.

If processor 310 determines that there are no preprogrammed motionpatterns (“no” in step 404), then in step 406 processor 310 may causeaccount card 110 to request a motion pattern by prompting user 105 toperform a physical gesture while holding account card 110. In someembodiments, account card 110 may provide a prompt via display 320, suchas a message and/or colored LED or light pattern, to perform a physicalgesture. In other embodiments, account card 110 may include a soundgenerator (not shown in figures) such as a speaker or beeper, forprompting user 105 to perform a physical gesture.

In step 408, processor 310 may detect a motion pattern sensed usingsensors 350, in response to the physical gesture performed by user 105.

In step 410, processor 310 may verify the detected motion pattern. Inprocess 400, processor 310 may verify the detected motion pattern byprompting user 105 to perform the physical gesture a second time,producing a motion pattern that matches the first motion pattern. Inother embodiments, account card 110 may prompt user 105 to select one ofinput devices 360 to indicate whether the motion pattern is verified, orshould be cleared and detected again.

In step 412, processor 310 may determine whether pattern is verifiedfrom step 410. If the motion pattern is not verified (“no” in step 412),then process 400 may return to step 406 and account card 110 may requesta new motion pattern. If the motion pattern is verified (“yes” in step412), then in step 414 processor 310 may store the motion pattern inmemory 330, for use as a reference pattern for comparing subsequentlydetected motion patterns. After storing the motion pattern, process 400may end. After a predetermined period of time, account card 110 maypower off. In some embodiments, account card 110 may additionally oralternatively power off when a level of electricity generated orprovided by power source 340 falls below a predetermined threshold.

FIG. 5 is a flowchart of another exemplary account card setup process500. As described below, process 500 is performed using mobile device115 (such as processor 230) in combination with processor 311 to setupaccount card 110.

In step 502, processor 311 may activate account card 110, similar tostep 402 described above with respect to FIG. 4. In some embodiments,processor 311 may also begin scanning available communication channelsfor mobile device 115 using antenna 370.

In step 504, mobile device 115 may launch account app 252. Account app252 may cause mobile device 115 to link wirelessly with account card 110via wireless communication between antennas 270 and 370 (step notshown).

In step 506, mobile device 115 may determine whether one or more motionpatterns are preprogrammed in account card 110. In some embodiments,mobile device 115 may query memory 340 of account card 110, to determineif any motion patterns are stored. If a motion pattern is stored onaccount card 110 (“yes” in step 506), then process 500 may end. If nomotion pattern is stored (“no” in step 506), then in step 508 mobiledevice 115 may request a motion pattern by prompting user 105 to performa physical gesture involving mobile device 115.

In step 510, mobile device 115 may detect a motion pattern using one ormore sensors 280.

In step 512, mobile device 115 may verify the detected motion pattern,similar to step 410 of process 400.

In step 514, mobile device 115 may determine if pattern is verified,similar to step 412 of process 400. If mobile device 115 determines thatthe detected motion pattern is not verified (“no” in step 514), process500 may return to step 508, and mobile device 115 may request an anothermotion pattern.

If mobile device 115 determines that the detected motion pattern isverified (“yes” in step 514), then in step 516, mobile device 115 maytransmit the verified motion pattern to account card 110 via antennas270 and 370. Account card 110 may store the received motion pattern inmemory 330 in step 518. After storing the received motion pattern,process 500 may end.

In some embodiments, process 500 may allow user 105 to attach one ormore settings to one or more motion patterns (not shown in figures).Using mobile device 115, user 105 may have access to a robust interfaceof options and features that may be associated with stored motionpatterns. For example, user 105 may create a first motion pattern thatcauses account card 110 to provide first account information, such as afirst account number. User 105 may also create a second motion patternthat may cause account card 110 to provide second account information,such as a second account number. In some embodiments, user 105 may storedifferent motion patterns for different users of account card 110,and/or different limitations on account card 110. For example, a firstmotion pattern may be stored for a first individual to use foractivating account card 110, and a second motion pattern may be storedfor a second individual to use for activating account card 110. Asanother example, a first motion pattern may activate account card 110with a first spending limit, and a second motion pattern may activateaccount card 110 with a second spending limit. Settings may beconfigured using mobile device 115, and transmitted to account card 110for storage in memory 340.

FIG. 6 is a flowchart of an exemplary account information transmissionprocess 600. As described herein, process 600 is performed by accountcard 110 processor 310. In some embodiments, one or more steps ofprocess 600 may be performed using a different processor, such asprocessor 230 of mobile device 115.

In step 602, processor 310 may power on account card 110. Similar tostep 402 of process 400, processor 310 may power on account card 110 inresponse to an input via input devices 360, kinetic power generation,detection of ambient power and inductive power, or based on data fromsensors 350 such as exceeding an ambient light threshold level.

In step 604, account card 110 may request a motion pattern by promptinguser 105 to perform a physical gesture. Similar to step 406 of process400, account card 110 may provide a visual indicator on display 320,instructing user 105 to perform a physical gesture. In some embodiments,account card 110 may include a beeper or speaker (not shown in figures)for providing an audible prompt to perform a physical gesture.

In step 606, processor 310 may detect a motion pattern corresponding toa physical gesture performed by user 105 using account card 110. In someembodiments, processor 310 may receive data from sensors 350 and processthe received data to detect the motion pattern.

In step 608, processor 310 may determine if the detected motion patternmatches at least one stored motion pattern in memory 330. In someembodiments, processor 310 may compare the detected motion pattern tostored motion patterns, such as motion patterns stored in processes 400and 500. In some embodiments, motion pattern comparison may comprise astatistical analysis of the detected and stored motion patterns,extracting features in sensor data for the motion patterns, anddetermining a similarity between the detected and stored motionpatterns. In some embodiments, processor 310 may employ a confidencelevel or probability score to determine whether the detected motionpattern matches at least one stored motion pattern.

If processor 310 determines that the detected motion pattern does notmatch any stored motion patterns (“no” in step 608), then in step 610processor 310 may determine whether a number of consecutive attemptshave exceeded a predetermined limit. In some embodiments, processor 310may determine whether a predetermined number of failed attempts haveoccurred in a predetermined time period. If not (“no” in step 610), thenprocess 600 may return to step 604, and account card 110 may requestanother motion pattern entry by prompting user 105 to perform anotherphysical gesture.

If attempts have exceeded a predetermined limit (“yes” in step 610) thenin step 612 processor 310 may deny usage of account card 110, and refuseto perform any function. Process 600 may then end. In some embodiments,processor 310 may allow additional attempts to use account card 110after another predetermined time period has elapsed.

Returning to step 608, if the detected pattern matches at least onestored motion pattern (“yes” in step 608), then in step 614 processor310 may determine if motion pattern is verified. In some embodiments,processor 310 may prompt user 105 to perform the same physical gestureagain to confirm the proper motion pattern. In other embodiments,processor 310 may determine whether the confidence value or probabilityscore exceeds a predetermined threshold (such as 95% or 0.95 confirmed).In such embodiments, processor 310 may determine that the motion patternis not verified if the confidence value is below the predeterminedthreshold, even though the motion pattern may be determined totentatively “match” a stored motion pattern.

If processor 310 determines that the motion pattern is not verified(“no” in step 614), then process 600 may return to step 604, and accountcard 110 may request a new motion pattern by prompting user 105 toperform another physical gesture.

If the detected motion pattern is verified (“yes” in step 614), then instep 616 processor 310 may initiate account information transmissionfrom account card 110 to card information receiver 120. In step 616,processor 310 may determine whether any settings and/or limits areassociated with the matched motion pattern. Processor 310 may thenretrieve account information associated with the matched motion pattern,the settings, and/or limits. Processor 310 may also activate one or moredata transmitters configured to provide the retrieved accountinformation. In some embodiments, processor 310 may write magneticstripe 380 to include the retrieved account information. In otherembodiments, processor 310 may enable antenna 370 to transmit accountinformation via near field communication or short range wirelesstransmission. In other embodiments, processor 310 may encode a radiofrequency ID (RFID) chip with the retrieved account information, orenable a RFID chip such as an EMV (Europay, Mastercard, Visa) chip tocommunicate with a contact or non-contact reader. In some embodiments,processor 130 may cause display 320 to display the retrieved accountinformation, when display 320 is capable of providing alphanumericcharacters.

In step 618, account card 110 may transmit account information viamagnetic stripe 380, antenna 370, or other suitable mechanism, to anexternal device such as card information receiver 120, for use by cardinformation recipient server 125. In some situations, if transmission isnot completed within a predetermined amount of time, account card 110may timeout.

After completion of account information transmission or a timeout,processor 310 may power off account card 110, and process 600 may end instep 620. In some embodiments, processor 310 may delete accountinformation from magnetic stripe 380 or any memory buffer in antenna370, and processor 310 may clear any account information transmissionmechanisms so that account information will not be provided again untilprocessor 310 receives another matching motion pattern. Thus, thedisclosed embodiments may provide a secure, motion pattern—typepassword—protected storage of account information, in a form factor thatis small, convenient, and able to be used with a vast infrastructure ofcard reading equipment.

The foregoing description has been presented for purposes ofillustration. It is not exhaustive and is not limited to the preciseforms or embodiments disclosed. Modifications and adaptations of theembodiments will be apparent from consideration of the specification andpractice of the disclosed embodiments. For example, the describedimplementations include hardware and software, but systems and methodsconsistent with the present disclosure can be implemented as hardwarealone.

Computer programs based on the written description and methods of thisspecification are within the skill of a software developer. The variousprograms or program modules can be created using a variety ofprogramming techniques. For example, program sections or program modulescan be designed in or by means of Java, C, C++, assembly language, orany such programming languages. One or more of such software sections ormodules can be integrated into a computer system, non-transitorycomputer-readable media, or existing communications software.

Moreover, while illustrative embodiments have been described herein, thescope includes any and all embodiments having equivalent elements,modifications, omissions, combinations (e.g., of aspects across variousembodiments), adaptations or alterations based on the presentdisclosure. The elements in the claims are to be interpreted broadlybased on the language employed in the claims and not limited to examplesdescribed in the present specification or during the prosecution of theapplication, which examples are to be construed as non-exclusive.Further, the steps of the disclosed methods can be modified in anymanner, including by reordering steps or inserting or deleting steps. Itis intended, therefore, that the specification and examples beconsidered as exemplary only, with a true scope and spirit beingindicated by the following claims and their full scope of equivalents.

1-30. (canceled)
 31. A user account apparatus for providing account information, comprising: a housing; a power source; a sensor; a data transmitter; at least one memory storing instructions and account information; and at least one processor configured to execute the stored instructions to perform operations comprising: receiving a predefined motion pattern from a mobile device in wireless communication with the user account apparatus; storing the predefined motion pattern in the memory; detecting, using the sensor, a user motion pattern corresponding to a physical gesture performed using the user account apparatus; analyzing the detected motion pattern using the predefined motion pattern; activating, based on the detected motion pattern, the data transmitter to provide the stored account information from the user account apparatus to a card information receiver; and transmitting, from the user account apparatus, the stored account information to the card information receiver.
 32. The apparatus of claim 31, wherein the power source comprises a wireless power receiver.
 33. The apparatus of claim 31, wherein the data transmitter comprises a magnetic stripe.
 34. The apparatus of claim 31, wherein the data transmitter comprises a near field communication chip.
 35. The apparatus of claim 31, wherein the detected motion pattern comprises a plurality of movements performed in a sequence.
 36. The apparatus of claim 31, wherein the operations further comprise deactivating the data transmitter after at least one of transmitting the stored account information or expiration of a predetermined period of time.
 37. the apparatus of claim 31, wherein the operations further comprise storing at least a first motion pattern for a first user and a second motion pattern for a second user in the memory.
 38. The apparatus of claim 31, wherein the operations further comprise establishing settings for a plurality of users.
 39. The apparatus of claim 38, wherein the settings are associated with a financial service provider.
 40. The apparatus of claim 39, wherein the operations further comprise communicating with a financial service provider server.
 41. A system for providing account information from a user account apparatus, comprising: a housing; a power source; a sensor; a data transmitter; at least one memory storing instructions and account information; and at least one processor configured to execute the stored instructions to perform operations comprising: receiving a predefined motion pattern from a mobile device in wireless communication with the user account apparatus; storing the predefined motion pattern in the memory; detecting, using the sensor, a user motion pattern corresponding to a physical gesture performed using the user account apparatus; analyzing the detected motion pattern using the predefined motion pattern; activating, based on the detected motion pattern, the data transmitter to provide the stored account information from the user account apparatus to a card information receiver; and transmitting, from the user account apparatus, the stored account information to the card information receiver.
 42. The system of claim 41, wherein the power source comprises a wireless power receiver.
 43. The system of claim 41, wherein the data transmitter comprises a magnetic stripe.
 44. The system of claim 41, wherein the data transmitter comprises a near field communication chip.
 45. The system of claim 41, wherein the detected motion pattern comprises a plurality of movements performed in a sequence.
 46. The system of claim 41, wherein the operations further comprise deactivating the data transmitter after at least one of transmitting the stored account information or expiration of a predetermined period of time.
 47. The system of claim 41, wherein the operations further comprise storing at least a first motion pattern for a first user and a second motion pattern for a second user in the memory.
 48. The system of claim 41, wherein the operations further comprise establishing settings for a plurality of users.
 49. The system of claim 48, wherein the settings are associated with a financial service provider.
 50. The system of claim 49, wherein the operations further comprise communicating with a financial service provider server. 